Skip to content

Conversation

@pkriens
Copy link
Member

@pkriens pkriens commented Feb 14, 2025

The code from source code generation required the bundle to be part of the repositories, it did not support 'version=file'. This was added. If this throws an exception, we fall back to the old way.
Basic change is that we now use the Project's getBundles to get the class path while we use Workspace.getBundle. The Workspace was used since this could also be used in bndrun files but a bndrun file is also a Project ... The Project.getBundles probably belongs on Workspace ...


Signed-off-by: github-actions [email protected]

---
 Signed-off-by: github-actions <[email protected]>

Signed-off-by: github-actions <[email protected]>
@pkriens pkriens changed the title Allow class path to come from file system -generated – Allow class path to come from file system Feb 14, 2025
@chrisrueger chrisrueger changed the title -generated – Allow class path to come from file system -generate – Allow class path to come from file system Feb 14, 2025
@pkriens pkriens closed this Apr 14, 2025
@pkriens
Copy link
Member Author

pkriens commented Apr 14, 2025

I closed this because I solved the problem in another way. Instead of referring to a file with version=file, I am just wrapping the bad jar into a nice bundle.

However, this is very useful but I just don't have the time to finish this off.

A key missing feature is also to capture the output of the command, at least stderr, and show it on the errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant